System and method for detecting vehicle proximity in an electric vehicle supply equipment

ABSTRACT

A system and method is provided for detecting vehicle proximity in an electric vehicle supply equipment (EVSE). A sensor may be configured to detect a presence of a vehicle within a predetermined distance of the EVSE. A processor may be configured to determine that the vehicle is in proximity of the EVSE in response to the sensor detecting the presence of the vehicle. The processor may be further configured to generate an alert in response to a determination that the vehicle is in proximity of the EVSE.

TECHNICAL FIELD

The present disclosure relates to the field of electric vehicle supplyequipments. More specifically, the present disclosure relates todetecting vehicle proximity in electric vehicle supply equipments.

BACKGROUND

An electric vehicle supply equipment supplies electric energy forcharging/recharging of electric vehicles plugged into the equipment.Vehicle detection systems exist. However, an efficient way to detectvehicle proximity to an electric vehicle supply equipment is needed.

These and other drawbacks exist.

BRIEF SUMMARY

Various systems, computer program products, and methods for detectingvehicle proximity in an electric vehicle supply equipment (EVSE) aredescribed herein.

According to one aspect of the present disclosure, the method mayinclude a plurality of operations. In some implementations, theoperations may include detecting, via a sensor, a presence of a vehiclewithin a predetermined distance of the EVSE. In some implementations,the operations may include determining, by at least one computingprocessor coupled to the sensor, that the vehicle is in proximity of theEVSE in response to the sensor detecting the presence of the vehicle. Insome implementations, the operations may include generating, by the atleast one computing processor, an alert in response to determining thatthe vehicle is in proximity of the EVSE.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are illustrated by way of example andare not limited by the accompanying figures with like referencesindicating like elements.

FIG. 1 illustrates an exemplary electric vehicle supply equipment,according to various aspects of the invention.

FIG. 2 illustrates components of an enclosure of the electric supplyequipment, according to various aspects of the invention.

FIG. 3 illustrates a flowchart depicting example operations performed byan electric vehicle supply equipment, according to various aspects ofthe invention.

DETAILED DESCRIPTION

FIG. 1 illustrates an exemplary electric vehicle supply equipment (EVSE)100, according to various aspects of the invention. EVSE 100 may includean enclosure 105 that houses one or more components of the EVSE 100.Externally, enclosure 105 may include, among other things, LED (lightemitting diode) lights 120, a display screen 122 (for example, liquidcrystal display or other display), an opening 130 that accepts a J1772plug 132 that is capable of charging electric and plug-in hybridelectric vehicles, and an authentication interface 135 that isconfigured to capture identifying information associated with thevehicle and/or a driver of the vehicle.

EVSE 100 may include a cord 110 of a particular length that ensures easycharging access over and around the electric vehicle. In someimplementations, the cord length may be 18 feet, though other cordlengths may be used without departing from the scope of the invention.In some implementations, cord 110 may include one or more cables used tosupply electric energy for charging/recharging of electric vehiclesplugged into the EVSE 100.

EVSE 100 may include a bracket 115 for coiling/storing cord 110 after acharging session (i.e., after charging of a vehicle). In someimplementations, the bracket 115 may be formed of stainless steel,though other materials may be used without departing from the scope ofthe invention.

In some implementations, EVSE 100 may be communicatively coupled toremote server 150 via link or network 145. In some implementations, linkor network 145 may include a Local Area Network, a Wide Area Network, acellular communications network, a Public Switched Telephone Network, awireless communication network, and/or other network or combination ofnetworks.

In some implementations, as depicted in FIG. 2, enclosure 105 of EVSE100 may include a sensor 220, a processor 230, a memory 240, displayscreen 122, speaker 250, LED lights 120, authentication interface 135,and/or other components that facilitate the functions of EVSE 100. Insome implementations, processor 230 includes one or more processorsconfigured to perform various functions of EVSE 100. In someimplementations, memory 240 includes one or more tangible (i.e.,non-transitory) computer readable media. Memory 240 may include one ormore instructions that when executed by processor 230 configureprocessor 230 to perform functions of EVSE 100.

In some implementations, sensor 220 may be configured to detect apresence of a vehicle within a predetermined distance of the EVSE 100.In some implementations, sensor 220 may be mounted or attached toenclosure 105 and may be coupled to the processor 230. In someimplementations, sensor 220 may include a ranging sensor. A rangingsignal transmitted by the ranging sensor may be reflected by a vehicleapproaching the EVSE 100. The reflected ranging signal may be used todetect the presence of the vehicle within a particular distance of theEVSE 100. In some implementations, the ranging sensor may be configuredto operate based on radio frequency spectrum, an audio spectrum, visibleand/or non-visible light.

In some implementations, sensor 220 may include an imaging sensor (forexample, in a video camera) configured to detect a presence of a vehiclewithin a predefined area (or distance) visible via the sensor. In someimplementations, the predefined area may include a parking space. Insome implementations, the imaging sensor may be configured to detect thepresence of the vehicle within 20 feet of the EVSE. In someimplementations, the imaging sensor may be configured to the capture aplurality of video images of the predefined area, analyze the capturedvideo images, and detect the presence of the vehicle based on theanalysis (for example, detect that a vehicle has entered, parked in, orexited a parking spot).

In some implementations, sensor 220 may include a magnetic sensorconfigured to use magnetic fields. The magnetic sensor may include aloop of wire embedded in the pavement, road, and/or parking space. Insome implementations, the loop is energized from a high frequencyvoltage source while the coil current is measured. When a vehicle isparked over the coil the coil's inductance will increase resulting in adecrease in coil current. This is caused by vehicle's steel frame,wheels, etc. The decrease in current indicates a presence of a vehicle.

In some implementations, the coil may be energized from a currentsource. In these implementations, the increase in coil inductance causedby the vehicle will increase the coil's voltage.

In some implementations, processor 230 may be configured to determinethat the vehicle is in proximity of the EVSE 100 in response to thesensor detecting the presence of the vehicle. In some implementations,sensor 220 may communicate a sensing signal to the processor 230indicating that the presence of a vehicle has been detected. In someimplementations, processor 230 may receive the sensing signal anddetermine that the vehicle is in proximity of the EVSE 100.

In some implementations, in response to a determination that the vehicleis in proximity of the EVSE 100, processor 230 may generate at least onealert. In some implementations, the alert may include an audible alert.In some implementations, EVSE 100 may include a speaker 250 that isconfigured to provide the audible alert. The audible alert may be in theform of a male/female voice sounding a verbal alert, and/or otheraudible alerts. In some implementations, the alert may include a visualalert. In some implementations, LED lights 120 and/or display screen 122may be used to provide visual alerts. In some implementations, LEDlights 120 may produce a light pattern to indicate that a vehicle is inproximity of the EVSE 100. In some implementations, display screen 122may display a visual message for the driver of the vehicle in responseto the determination that the vehicle is in proximity of the EVSE 100.In some implementations, the alert may include a message communicated byEVSE 100 to remote server 150 regarding the vehicle's presence/proximityat/to the EVSE 100.

In some implementations, the alert may include a notification to adriver of the vehicle determined to be in proximity of the EVSE 100 toprovide identifying information. In some implementations, identifyinginformation may include identification of the driver, an identificationof the vehicle, an account number, and/or other identifying information.

In some implementations, the notification may include a message for thedriver to provide identifying information via authentication interface135. In some implementations, identifying information may be provided bytapping a smart card, chip card, or other integrated circuit card (ICC)containing the identifying information (i.e., the card may store theidentifying information) against the authentication interface 135. Insome implementations, identifying information may be provided bybringing a contactless smart card, chip card, or other integratedcircuit card (ICC) containing the identifying information in proximityof the authentication interface 135. In some implementations,authentication interface 135 may include a card reader that isconfigured to read the identifying information from the smart card (viaradio frequency induction technology, for example).

In some implementations, the identification of the vehicle may bereceived by scanning and reading the vehicle's license plate (via animaging sensor described above, for example).

In some implementations, authentication interface 135 may provide theobtained identifying information to processor 230. In someimplementations, processor 230 may authenticate the driver and/orvehicle based on the obtained identifying information. In someimplementations, processor 230 may determine that the driver and/orvehicle is legitimate based on the obtained identifying information. Insome implementations, a list of users registered to use EVSE 100 may bestored in memory 240. In some implementations, a list of users and/ortheir vehicles may be stored in memory 240. In some implementations,processor 230 may compare the obtained identifying information with thelist stored in the memory 240. In some implementations, processor 230may determine that charging of the vehicle using the EVSE 100 may beinitiated in response to a match. In some implementations, processor 230may determine that the charging of the vehicle using the EVSE 100 maynot be initiated if there is no match.

In some implementations, authentication interface 135 may communicatethe obtained identifying information to remote server 150. In someimplementations, server 150 may include a processor and memory (nototherwise illustrated in the Figures). In some implementations, theserver processor may authenticate the driver and/or vehicle based on theobtained identifying information. In some implementations, the serverprocessor may determine that the driver and/or vehicle is legitimatebased on the obtained identifying information. In some implementations,a list of users registered to use EVSE 100 may be stored in the servermemory. In some implementations, a list of users and/or their vehiclesmay be stored in the server memory. In some implementations, the serverprocessor may compare the obtained identifying information with the liststored in the server memory. In some implementations, the serverprocessor may determine that charging of the vehicle using the EVSE 100may be initiated in response to a match. In some implementations, theserver processor may determine that the charging of the vehicle usingthe EVSE 100 may not be initiated if there is no match.

In some implementations, the alert may include a notification to thedriver of the vehicle that the driver and/or vehicle have beenauthenticated and to provide payment information for the chargingtransaction (i.e., charging of the vehicle). In some implementations, inresponse to a determination that the vehicle is in proximity of the EVSE100 and/or in response to a determination that the driver and/or vehicleis legitimate, the alert to provide payment information may be provided.In some implementations, the driver may use the smart card to providepayment information (i.e., to pay for the charging transaction) viaauthentication interface 135.

In some implementations, when the requested payment information isreceived, another alert may be provided to the driver of the vehicle toinitiate charging of the vehicle using the EVSE 100. Once charging iscomplete, the driver may be notified that the charging of the vehicle iscomplete and a payment amount (funds to pay for the chargingtransaction) is charged based on the payment information (obtained fromthe smart card, for example).

In some implementations, the smart card may be loaded with funds to payfor the charging transaction. In these implementations, authenticationinterface 135 may receive an indication of the preloaded funds in thesmart card (i.e., payment information). Once charging is complete, thepayment amount may be debited from the preloaded funds.

In some implementations, the payment information may include an accountnumber associated with the driver. In these implementations,authentication interface 135 may obtain the account number associatedwith the driver from the smart card and may communicate the accountnumber to server 150. In some implementations, server 150 maycommunicate with the appropriate financial institution to obtain thefunds to pay for the charging transaction.

In some implementations, the alert may include a notification to thedriver of the vehicle that a transaction time for paying for thecharging transaction has been exceeded. In some implementations, thealert may include a notification to the driver of the vehicle that thedriver has failed to provide identifying information and/or otherrequested information within a preset time period.

In some implementations, one or more of the above notifications may beprovided via speaker 250 and/or display screen 122. In someimplementations, one or more of the above notifications may becommunicated to remote server 150.

FIG. 3 is a flowchart 300 depicting example operations performed by theEVSE 100, according to various aspects of the invention. In someimplementations, the described operations may be accomplished using oneor more of the modules/components described herein. In someimplementations, various operations may be performed in differentsequences. In other implementations, additional operations may beperformed along with some or all of the operations shown in FIG. 3. Inyet other implementations, one or more operations may be performedsimultaneously. In yet other implementations, one or more operations maynot be performed. Accordingly, the operations described are exemplary innature and, as such, should not be viewed as limiting.

In an operation 310, process 300 may detect presence of a vehicle withina predetermined distance of the EVSE 100. In an operation 312, process300 may determine that the vehicle is in proximity of the EVSE 100 inresponse to detecting the presence of the vehicle. In an operation 314,process 300 may generate at least one alert in response to thedetermination that the vehicle is in proximity of the EVSE 100.

Implementations of the invention may be made in hardware, firmware,software, or various combinations thereof. The invention may also beimplemented as computer-readable instructions stored on a tangiblecomputer-readable storage medium which may be read and executed by oneor more processors. A computer-readable storage medium may includevarious mechanisms for storing information in a form readable by acomputing device. For example, a tangible computer-readable storagemedium may include optical storage media, flash memory devices, and/orother storage mediums. Further, firmware, software, routines, orinstructions may be described in the above disclosure in terms ofspecific exemplary aspects and implementations of the invention andperforming certain actions. However, it will be apparent that suchdescriptions are merely for convenience, and that such actions may infact result from computing devices, processors, controllers, or otherdevices executing firmware, software, routines or instructions.

Other embodiments, uses and advantages of the invention will be apparentto those skilled in the art from consideration of the specification andpractice of the invention disclosed herein. The specification should beconsidered exemplary only, and the scope of the invention is accordinglyintended to be limited only by the following claims.

What is claimed is:
 1. An electric vehicle supply equipment (EVSE) forcharging a vehicle by a user of the vehicle comprising: a cord having apredetermined distance between a vehicle and the EVSE that ensurescharging access; one or more image sensors configured to detect apresence of a vehicle within the predetermined distance of the EVSE;wherein charging of the vehicle is performed based on vehicleidentifying information obtained via the one or more image sensors; aprocessor configured to: determine that the vehicle is in proximity ofthe EVSE in response to detecting the presence of the vehicle; andgenerate an alert in response to a determination that the vehicle is inproximity of the EVSE; after the determination that the vehicle is inproximity of the EVSE, authenticate the user based on user identifyinginformation; and initiate charging of the vehicle based on theauthentication of the user and vehicle identifying information.
 2. Theequipment of claim 1, wherein the alert comprises an audible alert. 3.The equipment of claim 1, wherein the alert comprises a visual alert. 4.The equipment of claim 1, wherein the processor is further configured tocommunicate a message to a remote server regarding the proximity of thevehicle to the EVSE.
 5. The equipment of claim 1, wherein the processoris further configured to generate a second alert that comprises anotification to the user of the vehicle to provide payment informationfor the charging of the vehicle, wherein the second alert is generatedin response to user authentication.
 6. The equipment of claim 1, whereinthe alert comprises a notification to the user of the vehicle to providethe identifying information.